exchange server

Change page: < 1 2 3 4 5 6 7 8 > | Displaying page 1 of 8, items 1 to 30 of 215.

Microsoft Exchange Server 2013 : Designing a Successful Exchange Storage Solution (part 3) - Selecting the Right Storage Hardware, Storage Validation Using Jetstress

Now we can move on to selecting appropriate hardware for our requirements. There are many aspects to this decision, and the requirements that we have identified so far represent only a few of them.

Microsoft Exchange Server 2013 : Designing a Successful Exchange Storage Solution (part 2) - Making Sense of the Exchange Mailbox Server Role Requirements Calculator

The Exchange 2013 Server Role Requirements Calculator, or storage calculator as it used to be known, is basically a complicated Excel spreadsheet that contains the calculations necessary to take your design requirements, and turn them into some storage-specific requirements.

Microsoft Exchange Server 2013 : Designing a Successful Exchange Storage Solution (part 1) - Requirements Gathering

From an Exchange storage design perspective, we are mainly interested in the service level because it drives our high-availability decisions.

Microsoft Exchange Server 2013 : Designing a Successful Exchange Storage Solution - Storage Improvements in Exchange Server 2013

This is the single most important change in Exchange Server 2013. Quite simply, automatic database reseed makes deploying a JBOD storage solution viable for many organizations that found JBOD too difficult to manage in Exchange Server 2010.

Microsoft Exchange Server 2013 : Designing a Successful Exchange Storage Solution - Storage Changes in Exchange 2013

Exchange Server 2013 is a major new release and, as such, the Exchange product group invested in the key development areas that were projected to yield the largest benefits to both customers and the teams that run Exchange Online.

Microsoft Exchange Server 2013 : Designing a Successful Exchange Storage Solution - A Brief History of Exchange Storage

As mentioned, Exchange has been around for quite a while, and it has been adapted to the changing landscape of email.

Exchange Server 2013 Management and Maintenance Practices (part 7) - Weekly Maintenance, Monthly Maintenance, Quarterly Maintenance

Tasks that do not require daily administrative input, but that still require frequent attention, are categorized as weekly maintenance routines. Recommended weekly maintenance routines are described in the following sections.

Exchange Server 2013 Management and Maintenance Practices (part 6) - Prioritizing and Scheduling Maintenance Best Practices

Exchange Server 2013 is a very efficient messaging system. However, as mailboxes and public folders are used, there is always the possibility of the logical corruption of data contained within the databases.

Exchange Server 2013 Management and Maintenance Practices (part 5) - Message Tracking

Of the auditing techniques available in Exchange Server, message tracking is by far the least resource intensive and will likely be the most commonly used by administrators. Because this feature has proven so valuable in previous versions of Exchange Server, Microsoft has enabled it by default in Exchange Server 2013.

Exchange Server 2013 Management and Maintenance Practices (part 4) - SMTP Logging

Logging SMTP protocol activity provides administrators with a powerful tool when troubleshooting issues with message delivery. By enabling SMTP logging, administrators can capture the SMTP conversations with email servers during message transport.

Exchange Server 2013 Management and Maintenance Practices (part 3) - Auditing the Environment

Various methods of auditing the Exchange Server environment exist to gather and store records of network and Exchange Server access and to assist with the monitoring and tracking of SMTP connections and message routing.

Exchange Server 2013 Management and Maintenance Practices (part 2) - Remote Connectivity Analyzer

The Remote Connectivity Analyzer (RCA) is also found in the Exchange Toolbox in Exchange Server 2013. The RCA allows administrators to test services from outside their organizations.

Exchange Server 2013 Management and Maintenance Practices (part 1) - Maintenance Tools for Exchange Server 2013

Several tools are available to administer and manage an Exchange Server 2013 environment. There are functions within the Exchange Administration Center, an automation and scripting shell, and several tools native to the Windows Server 2008/2012 operating systems.

Installing Exchange Server 2010 : Command-Line Setup (part 2) - Command-Line Server Recovery Options , Command-Line Delegated Server Installation , Installing Language Packs

There may come a time when you have to recover an Exchange server from a backup. This process will involve rebuilding the Windows server, then reinstalling Exchange Server using the Recover Server mode

Installing Exchange Server 2010 : Command-Line Setup (part 1) - Command-Line Installation Options

By and large, the server role installation options are probably the most useful for a typical person installing or configuring Exchange. They are certainly the most numerous.

Installing Exchange Server 2010 : Graphical User Interface Setup

The simplest way to install Exchange Server 2010 is to use the graphical user interface (GUI). The GUI will be sufficient for most Exchange Server installations.

Installing Exchange Server 2010 : Preparing for Exchange 2010 Ahead of Time (part 2) - Preparing the Active Directory Forest,Preparing Additional Domains

To run the forest preparation, you must be logged on with a user who is a member of the Enterprise Admins group. Further, you should run the forest preparation process from a server that is in the same Active Directory site and domain that holds the schema master flexible single master of operations (FSMO) role.

Installing Exchange Server 2010 : Preparing for Exchange 2010 Ahead of Time (part 1) - Existing Exchange Organizations , Preparing the Schema

If you have any Exchange 2003 servers in your organization, you must first prepare each domain so that Exchange Server 2010 can properly communicate with Exchange 2003 and so that Exchange 2003 can access certain newly created attribute sets in Active Directory.

Securing an Exchange Server 2007 Environment : Securing Outlook Web Access

Outlook Web Access (OWA) provides the interface for users to access their mail across the Internet utilizing a web browser. With the implementation of OWA 2003, Microsoft improved the features and performance of the product until it was almost as powerful as the actual Microsoft Outlook client.

Securing an Exchange Server 2007 Environment : Protecting Against Spam (part 2) - Filtering Junk Mail

Both Outlook 2003 and Outlook 2007 allow users to create and manage their own Safe Senders and Blocked Senders. As the name implies, the Safe Senders list is made up of user-defined addresses or domains, and messages from these addresses or domains will never be treated as junk email.

Securing an Exchange Server 2007 Environment : Protecting Against Spam (part 2) - Filtering Junk Mail

This feature has been improved with each new revision and is useful in minimizing the need for end users to configure junk mail filtering options. In fact, junk mail filtering is primarily controlled by Exchange administrators. However, some options can be configured by the users.

Securing an Exchange Server 2007 Environment : Protecting Against Spam (part 1) - Protecting Against Web Beaconing

A common and very popular format for email messages is Hypertext Markup Language, or HTML. This format is so popular because of the rich content that can be presented, including graphics, images, font formatting, and more

Securing an Exchange Server 2007 Environment : Securing Outlook 2007 (part 2) - Encrypting Communications Between Outlook and Exchange , Blocking Attachments

A common and often effective way for viruses and malicious scripts to spread from user to user is through email. When a user receives a message with an attachment, simply opening the attachment can allow the virus to activate and, if proper security measures are not in place, the virus can do damage to the system or spread to other users.

Securing an Exchange Server 2007 Environment : Securing Outlook 2007 (part 1) - Outlook Anywhere

Prior to Exchange Server 2003, Outlook users who needed to connect to Exchange over the Internet had to establish a virtual private network (VPN) connection prior to using Outlook.

Securing an Exchange Server 2007 Environment : Securing Your Windows Environment (part 3) - Keeping Up with Security Patches and Updates

With Windows Server 2003, Windows Vista, and Windows XP, utilities exist that allow you to automate this process and simplify the distribution of updates. Microsoft has provided several options: Windows Update, Microsoft Update, Microsoft Windows Server Update Services (WSUS), and Microsoft Systems Management Server (SMS)

Securing an Exchange Server 2007 Environment : Securing Your Windows Environment (part 2) - Utilizing Security Templates

Security templates are a practical and effective means to apply standardized security policies and configurations to multiple systems in an environment.

Securing an Exchange Server 2007 Environment : Securing Your Windows Environment (part 1) - Windows Server 2003 Security Improvements , Windows Vista Security Improvements

Windows Vista complements Windows Server 2003 from the client perspective by supporting the security features embedded in Windows Server 2003.

Securing an Exchange Server 2007 Environment : Client-Level Secured Messaging - Exchange Server 2007 Client-Level Security Enhancements

As mentioned earlier, Exchange Server 2007 has several improved security features—especially when combined with Outlook 2007.

Microsoft Exchange Server 2010 Requirements : Additional Requirements

In addition to making sure that the hardware and server software can support Exchange Server 2010, there are a few infrastructure requirements that you need to consider.

Microsoft Exchange Server 2010 Requirements : Software Requirements (part 2) - Windows Server Roles and Features

Windows Server 2008 breaks down the additional Windows components into roles and features. Depending on the Exchange 2010 roles, Windows Server 2008 will require additional Windows Server roles and features to be installed.